Minimal proxy pattern for Checker / Policy contracts #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…dvanced test contracts
This was
linked to
issues
Jan 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, Excubiae lets you deploy your specific Checker with specific parameters (like a set of external addresses for verifiers - used to verify the attributes / criteria). Same for Policy contracts—you tie them to one Checker. If you want different parameters for different contracts, you have to redeploy everything from scratch every time. This is gas-consuming and not dev friendly.
This PR aims to implement a Minimal Proxy Pattern (Clones with immutable args) using the Solady LibClone library. This would be a huge pro at just some contract writing overhead for byte per byte variable decomposition for immutability.
--
TODO